DO NOT MERGE — CI check for the v1.0.0 release tree - #92
Closed
Xof wants to merge 1 commit into
Closed
Conversation
Temporary — same-history carrier for the exact file content on release/v1.0.0 (an orphan branch GitHub won't open a PR against), so CI can run against it before that branch replaces main's history. Not meant to be merged normally.
🚦 Bench results: PR vs main
Per-scenario detail (4 metrics × cells)document-store
mutation-log
ycsb-a
ycsb-b
|
Collaborator
Author
|
Superseded — the release tree changed (crates.io/PyPI package rename to chisel-storage, dependency security fix, publish workflows added). New CI-check PR incoming for the updated tree. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Do not merge
This PR exists only to get a real CI run against the exact tree that's sitting on `release/v1.0.0` (an orphan commit with no shared history with `main`, which GitHub won't open a PR against directly). The diff below is the real content delta — just the version bump, 7 files.
Once CI is green here, this PR should be closed without merging. The actual history swap happens separately via `release/v1.0.0` (see the other open PR/instructions), not through this one.